Communication system to provide selective access to a wireless communication device

ABSTRACT

A communication system provides selective access to target wireless communication devices. A naming server system receives naming system registration messages from target wireless communication devices and address requests from user devices. The naming server system determines if the current time is within the access schedule for the target wireless communication device. If the current time is within the access schedule for the target wireless communication device, then the naming server system returns the IP address for the target wireless communication device. If the current time is not within the access schedule for the target wireless communication device, then the naming server system will respond with a timeframe when the target wireless communication device will be available for access.

TECHNICAL BACKGROUND

Domain names are data strings that can be used to access resources overdata networks. The domain names are often selected to ease userretention of the name. A prime example of a domain name is “uspto.gov”for the U.S. Patent Office. A Domain Naming System (DNS) stores andserves information associated with domain names. A prime example of theassociated information is the current Internet Protocol (IP) addressesthat can be used to communicate with resources in the domain. A commontask for a DNS is the translation of domain names into theircorresponding IP addresses. For example, a DNS would translate uspto.govinto the IP address of a Patent Office server system. The user thencommunicates with the Patent Office over the Internet using the IPaddress.

To load the DNS, Internet servers register their IP addresses with theDNS in association with their domain names. While these registrationsare active, the DNS will serve out the IP addresses in response toqueries having the domain names. Eventually, a given IP addressregistration may time-out, and the DNS will require another registrationbefore serving out the IP address. In other scenarios, a properlyregistered IP address may still fail the user due to another reason,such as network or server problems. In addition to the IP address, theDNS may associate other information with the domain names, such as callstate and network state.

Wireless communication devices are increasingly being used as contentservers that interact with the DNS to provide their content over theInternet (or a private IP network). For example, a wireless camerahaving a domain name and an IP address may register the name and IPaddress with the DNS to serve out live images from the camera. Thesewireless communication devices may have limited availability due topower restraints, network availability, and the like. Unfortunately, thewireless devices and the DNS are not properly configured for efficientand effective interaction in the developing wireless environment.

TECHNICAL OVERVIEW

A communication system provides selective access to target wirelesscommunication devices. A naming server system receives naming systemregistration messages from target wireless communication devices andaddress requests from user devices. The naming server system determinesif the current time is within the access schedule for the targetwireless communication device. If the current time is within the accessschedule for the target wireless communication device, then the namingserver system returns the IP address for the target wirelesscommunication device. If the current time is not within the accessschedule for the target wireless communication device, then the namingserver system will respond with a timeframe when the target wirelesscommunication device will be available for access.

DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a communication system to provide selective access toa wireless communication device.

FIG. 2 illustrates the operation of a communication system to provideselective access to a wireless communication device.

FIG. 3 illustrates an operation of the communication system to provideselective access to a wireless communication device.

FIG. 4 illustrates an LTE communication system to provide selectiveaccess to a wireless communication device.

FIG. 5 illustrates a wireless communication device that interacts with anaming system to allow selective access.

FIG. 6 illustrates a naming server system that provides selective accessto wireless communication devices.

DETAILED DESCRIPTION

FIG. 1 illustrates communication system 100 that provides selectiveaccess to target wireless communication devices 101-103. Communicationsystem 100 comprises: target wireless communication devices 101-103(also referred to herein as “target devices”), naming server system 110,user devices 111-113, communication network 120, and communication links121-127. Target wireless communication devices 101-103 might be phones,computers, cameras, sensors, or some other machine having wirelesstransceivers and control circuitry.

In communication system 100, target wireless communication devices101-103 register their names and network addresses with naming serversystem 110. The registrations also include access schedules. Namingserver system 110 serves out the network addresses and/or future accesstimeframes to user devices 111-113 based on the access schedule.

FIG. 2 illustrates the operation of communication system 100 to provideselective access to target wireless communication devices 101-103.Target wireless communication devices 101-103 transfer naming systemregistration messages (also referred to herein as “registrationmessages”) for delivery to naming server system 110 (201). The namingsystem registration messages indicate the associated domain names andaccess schedules for target devices 101-103. The naming systemregistration messages may also indicate network addresses for targetdevices 101-103, although the network addresses could be provided later.

Note that a single target device may have multiple names, addresses, andaccess schedules, or that multiple target devices may share names,addresses, and access schedules. The domain names comprise data strings,such as Uniform Resource Identifiers (URIs) and the like. The accessschedules control whether naming server system 110 serves out thenetwork addresses, or whether naming system 110 suggests a subsequenttimeframe to obtain the network address from naming system 110.Typically, the access schedules correspond to when target devices101-103 will have adequate content, power, and network connectivity.

Naming server system 110 receives the naming system registrationmessages transferred by target wireless communication devices 101-103(202). Naming server system 110 stores the provided data in associationwith the respective domain name. One example of naming server system 110is a DNS server, although other naming server systems could be used.

Naming server system 110 receives address requests from user devices111-113 (203). The address requests indicate the domain names for targetwireless communication devices 101-103. Naming server system 110processes the domain names and their associated access schedules todetermine whether the current time is within the access schedules forthe target wireless communication devices (204). If naming server 110determines that the current time is within the access schedule of thetarget wireless communication device (205), then naming server system110 responds with the address for the target wireless communicationdevice (206). If naming server system 110 determines that the currenttime is not within the access schedule of the target wirelesscommunication device (205), then naming server system 110 responds witha timeframe to re-send the address request (207).

In the above operation, target wireless communication devices 101-103and naming server system 110 effectively and efficiently interact toconserve resources across communication system 100. Target wirelesscommunication devices 101-103 are not required to maintain the overlyburdensome content, power, or network connectivity that is required toremain on-net. User devices 111-113 are not required to continuallyrequest address translations until the target devices become available.Likewise, naming server system 110 should also handle a lower amount offailed address requests. In addition, communication network 120 handlesa lower amount of failed address requests to naming server system 110.Communication network 120 also handles a lower amount of failed datatransmissions that are directed to unavailable the target devices.

In some examples, the access schedule is a simple pre-determined set oftime periods, such as 9:00-11:00 PM on Mondays and Fridays. In otherexamples, the access schedule reflects an estimated future time when thetarget device expects to have adequate power, presence at a location,network connectivity, content access, and the like. In yet otherexamples, the access schedule reflects a calculated time-to-live for thetarget device power supply, presence at a location, estimated eventtime, network connectivity, and the like. In further examples, theaccess schedule is determined based on a trigger for the target device,such as: atmospheric conditions, temperature, wind speeds, motion,presence in a geographic location, network status, radio frequencynetwork, and the like.

Consider an example where the target wireless device is solar poweredsensor with limited battery capacity. Due to the amount of sun andusage, the battery power varies. The target device may then vary itsaccess schedule in accord with changing solar and usage conditions. Forexample, the target device may reduce the length of time content isserved during periods of reduced sun or periods of increased powerusage.

Some target devices may trigger data availability based on conditions.For example, a target atmospheric sensor may register for 2-hours ofcontent access starting in twelve hours in response to extreme CO₂levels. A target security camera may register for ten minutes of contentaccess starting immediately in response to unauthorized motiondetection.

FIG. 3 illustrates an operation of communication system 100 to provideselective access to target wireless communication devices 101-103.Naming server system 110 receives a naming system registration messagefrom target wireless device 101. The naming system registration messageindicates a domain name and includes an access schedule for targetwireless device 101. Naming server system 110 also receives an addressrequest from user device 111. Naming server system 110 compares thecurrent time with the access schedule for target wireless device 101.Since the current time is within the access schedule for target wirelessdevice 101, naming server system 110 sends the network address fortarget wireless device 101 to user device 111. Later user device 112requests access to target wireless device 101. Naming server system 110compares the current time with the access schedule for target wirelessdevice 101. The current time is no longer within the access schedule fortarget wireless device 101, so naming server system 110 responds with atimeframe when user device 112 should retry the address query.

FIG. 4 illustrates Long Term Evolution (LTE) communication system 400 toprovide selective access to wireless devices 401-403. LTE communicationsystem 400 provides an example of communication system 100, althoughcommunication system 100 may use alternative configurations andoperations. LTE communication system 400 comprises target devices401-403, eNodeB 405, S-GW 406, P-GW 407, DNS server 408, and userdevices 410-412. Target devices 401-403 comprise a gas meter, roboticCO₂ sensor, and truck camera. User devices 410-412 comprise a mobilephone, tablet, and computer.

In some examples, gas meter 401 is programmed to be available on the26th day of each month for ten minutes between 11:49 PM and 11:59 PM.Gas meter 401 registers with DNS server 408 with an access schedule thatindicates these available time periods. If DNS server 408 receives anaddress request for gas meter 401 before 11:49 on the 26th of the month,then DNS server 408 responds with the timeframe when a DNS retry shouldbe attempted—between 11:49 PM and 11:59 PM on the 26th day of the month.When the current time reaches 11:49 PM on the 26th day of the month,then DNS server 408 will begin to serve out the IP address of gas meter401. Thus, computer 412 may obtain the IP address of access gas meter401 to download information for billing purposes. If DNS server 408receives an address request for gas meter 401 after 11:59 on the 26th ofthe month, then DNS server 408 responds with the timeframe when a DNSretry should be attempted—between 11:49 PM and 11:59 PM on the 26th dayof the next month. If desired, the domain name and IP address would beavailable for use by other gas meters before and after 11:49 PM and11:59 PM on the 26th day of the month. In this way content downloads canbe batched and staggered for multiple gas meters.

In another example, robotic CO₂ sensor 402 determines its accessschedule based on an estimated future time for arrival in a geographicarea. This could be calculated based on distance and speed of travel.Robotic CO₂ sensor 402 would register with DNS server 408 to startserving its IP address after its estimated time of arrival. As a result,DNS server 408 will provide the estimated time of arrival in response toaddress queries for robotic CO₂ sensor 402 until the current timereaches the estimated time.

Alternatively, robotic CO₂ sensor 402 may wait until it reaches thegeographic area to register. Once robotic CO₂ sensor 402 detects that iswithin the geographic area, sensor 402 would then register with DNSserver 408 to begin serving its IP address immediately and for another 2hours—the length of time that robotic CO₂ sensor 402 remains within thegeographic area. DNS translations during this 2-hour time period wouldindicate the IP address for robotic CO₂ sensor 402 and indicate thetime-to-live at that geographic location.

In some examples, DNS server 408 will notify tablet 411 that robotic CO₂sensor 402 is available. In other examples, robotic CO₂ sensor 402 mayarrive at a specified geographic location but need to recharge itsbattery and will not be available until after a specified time torecharge. Different factors, such as type of power supply, remainingpower, network connectivity, content, geographic location, and the like,may be considered in determining the access schedule for robotic CO₂sensor 402. Alternatively, rather than determining the access schedulebased on detecting the device's presence in a pre-determine geographiclocation, robotic CO₂ sensor 402 may determine the access schedule basedan estimated future time when robotic CO₂ sensor 402 will be withinrange of a pre-determined radio frequency (i.e. a carrier's basestation) or when network load is expected to be low.

In another example, robotic CO₂ sensor 402 registers when it detects CO₂levels above a threshold. The access schedule for robotic CO₂ sensor 402is based on when registration is triggered and exact timeframes may notbe known in advance. In addition, the response provided by DNS server408 may also indicate the time remaining to access robotic CO₂ sensor402 (i.e. “device will be available for ten more minutes”). This couldbe based on power usage and remaining battery power among other factors.In yet another example, robotic CO₂ sensor 402 powers on and recordscontent when CO₂ levels are above a threshold. Robotic CO₂ sensor 402then registers when the device memory storage is at 80% capacity or whenbattery power is at 15% remaining.

In another example, truck camera 403 determines its access schedulebased on scheduled departure/arrival time and travel time. At thescheduled departure time, truck camera 403 powers on and registers withDNS server 408. The access schedule for truck camera 404 may indicatethat truck camera 403 will be available for the duration of the trip(i.e. “4 hours”). In other examples, truck camera 403 registers with DNSserver 408 when it detects it is located within a pre-determinedgeographic area and remains registered while located within a specifiedgeographic area. Alternatively, truck camera 403 powers up and registerswith DNS server 408 when it detects it is in motion and does notde-register until it has been stationary for a specified amount of time.

In some examples, truck camera 403 is accessible only by authorizedusers. The access schedule for truck camera 403 indicates a list ofapproved users in addition to the timeframe(s) that truck camera 403 isavailable. In this example, the list of approved users includes tablet411 and computer 412, but not mobile phone 410. When mobile phone 410requests access to truck camera 403, DNS server 408 determines mobilephone 410 is not on the list of approved users. DNS server 408 respondsthat access is denied. When computer 412 requests access during a timethat is within the access schedule for truck camera 403, DNS server 408responds with the IP address for truck camera 403.

FIG. 5 illustrates a target wireless communication device 500 thatinteracts with a naming system to allow selective access. Targetwireless device 500 is an example of the target wireless devices 101-103and 401-403, although these devices may use alternative configurationsand operations. Target wireless device 500 comprises communicationtransceiver 501 and processing system 502. Processing system 502includes processing circuitry 511 and memory 512 that stores software513. Software 513 comprises software modules 514-516.

Communication transceiver 501 comprises communication components, suchas antennas, amplifiers, filters, modulators, signal processingcircuitry, software, and the like. Communication transceiver 501 may beconfigured to use IP, Ethernet, and various wireless protocols—includingcombinations thereof. Communication transceiver 501 transfersregistration messages to a naming server system and transfers requestedcontent to requesting devices.

Processing circuitry 511 comprises microprocessor and other circuitrythat retrieves and executes operating software 513 from memory system512. Processing circuitry 511 may comprise a single device or could bedistributed across multiple devices—including devices in differentgeographic areas. Processing circuitry 511 may be embedded in varioustypes of equipment. Examples of processing circuitry 511 include centralprocessing units, application specific processors, and logic devices,and/or any type of computer processing devices—including combinationsthereof.

Memory system 512 comprises a non-transitory computer readable storagemedium readable by processing system 502 and capable of storing software513, such as a disk drive, flash drive, data storage circuitry, or someother hardware memory apparatus—including combinations thereof. Memorysystem 512 can include volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageof information, such as computer readable instructions, data structures,program modules, or other data—including combinations thereof. Memorysystem 512 may comprise a single device or could be distributed acrossmultiple devices—including devices in different geographic areas. Memorysystem 512 may be embedded in various types of equipment.

Software 513 comprises computer programs, firmware, or some other formof machine-readable processing instructions. Software 513 may include anoperating system, utilities, drivers, network interfaces, applications,or some other type of software. In this example, software 513 comprises:Naming Server module 514, Server module 515, and Application module 516,although software 513 could have alternative configurations in otherexamples.

Software 513 can be implemented in program instructions and can beexecuted by processing system 502. Software 513 can include additionalprocesses, programs, or components, such as operating system software,database software, or application software—including combinationsthereof. Software 513 can also comprise firmware or some other form ofmachine-readable processing instructions executable by processing system502.

When executed by processing system 502, software 513 directs processingsystem 502 to operate as described herein to interact with naming serversystems. In particular, Naming Server module 514 directs processingsystem 502 to transfer naming system registration messages with accessschedules for delivery to a naming server system. Server module 515directs processing system 502 to handle content requests to serve outthe requested content. Application module 516 directs processing system502 to develop content and access schedules.

FIG. 6 illustrates naming server system 600 that provides selectiveaccess to wireless communication devices. naming server system 600 is anexample of naming server system 110 and DNS server 408, although thesesystems may use alternative configurations and operations. Naming serversystem 600 comprises communication transceiver 601 and processing system602. Processing system 602 includes processing circuitry 611 and memory612 that stores software 613. Software 613 comprises software modules614-616.

Communication transceiver 601 comprises components that communicationover communication links such as network cards, ports, RF transceivers,processing circuitry and software, or some other communicationcomponents. Communication transceiver 601 may be configured tocommunication over metallic, wireless, or optical links. Communicationtransceiver 601 may be configured to use Time-Division Multiplexing(TDM), IP, Ethernet, optical networking, wireless protocols,communication signaling, or some other communication format—includingcombinations thereof. Communication transceiver 601 receivesregistration messages from target wireless communication devices andreceives address requests from user devices.

Processing circuitry 611 comprises microprocessor and other circuitrythat retrieves and executes operating software 613 from memory system612. Processing circuitry 611 may comprise a single device or could bedistributed across multiple devices—including devices in differentgeographic areas. Processing circuitry 611 may be embedded in varioustypes of equipment. Examples of processing circuitry 611 include centralprocessing units, application specific processors, and logic devices,and/or any type of computer processing devices—including combinationsthereof. Processing circuitry 611 processes the domain name and accessschedule for the requested target wireless communication device todetermine whether the current time is within the access schedule for thetarget wireless communication device.

Memory system 612 comprises a non-transitory computer readable storagemedium readable by processing system 602 and capable of storing software613, such as a disk drive, flash drive, data storage circuitry, or someother hardware memory apparatus—including combinations thereof. Memorysystem 612 can include volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageof information, such as computer readable instructions, data structures,program modules, or other data—including combinations thereof. Memorysystem 612 may comprise a single device or could be distributed acrossmultiple devices—including devices in different geographic areas. Memorysystem 612 may be embedded in various types of equipment. In someexamples, a computer apparatus could comprise memory system 612 andsoftware 613.

Software 613 comprises computer programs, firmware, or some other formof machine-readable processing instructions. Software 613 may include anoperating system, utilities, drivers, network interfaces, applications,or some other type of software. In this example, software 613 comprisesRegistration module 614, Address Request module 615, and Response module616, although software 613 could have alternative configurations inother examples.

Software 613 can be implemented in program instructions and can beexecuted by processing system 602. Software 613 can include additionalprocesses, programs, or components, such as operating system software,database software, or application software—including combinationsthereof. Software 613 can also comprise firmware or some other form ofmachine-readable processing instructions executable by processing system602.

When executed by processing system 602, software 613 directs processingsystem 602 to operate as described herein to provide selective access totarget wireless communication devices. In particular, Registrationmodule 614 directs processing system 602 to process the naming systemregistration message from target wireless communication devices toregister the target wireless communication devices. Address Requestmodule 615 directs processing system 602 to process the address requestsfrom user devices. Response module 616 directs processing system 602 totransfer responses to the address requests.

Referring back to FIG. 1, target devices 101-103 comprise any devicehaving wireless communication connectivity. Target devices 101-103comprise radio frequency (RF) communication circuitry, antenna, andsoftware elements. The RF circuitry typically includes amplifiers,filters, modulators, and signal processing circuitry. In some examples,target wireless device 101-103 includes circuitry and equipment toexchange wireless communications over wireless links with wirelessaccess system, transfer registration requests for DNS registration,transfer access schedules, and receive access requests from userdevices, among other operations. Target wireless devices 101-103 mayalso include user interface systems, memory devices, computer-readablestorage medium, software, processing circuitry, or other communicationcomponents. Target wireless devices 101-103 may be a sensor, computer,meter, camera, vehicle, appliance, electronic device that uploads dataor downloads available updates, or some other wireless communicationapparatus—including combinations thereof.

Naming server system 110 comprises a processing system and communicationtransceiver. Naming server system 110 may also include other componentssuch as a router, data storage system, and power supply. Naming serversystem 110 may reside in a single device or may be distributed acrossmultiple devices. Naming server system 110 may be a discrete system ormay be integrated within other systems—including other systems withincommunication system 100. In some examples, naming server system 110could comprise a network server system, network-attached storage,storage area network, home location register, visitor location register,

User devices 111-113 comprise any device having communicationconnectivity with hardware and circuitry programmed to function as acommunication device. User devices 111-113 are used to access the targetwireless communication devices. User devices 111-113 may also includeuser interface systems, memory devices, computer-readable storagemedium, software, processing circuitry, or other communicationcomponents. User devices 111-113 may be a computer, laptop, tablet,personal digital assistant (PDA), mobile phone, cellular phone,smartphone, machine transceivers, televisions, mobile Internet devices,and/or some other apparatus having networking components—includingcombinations thereof.

Communication network 120 is representative and may be a single wirelessnetwork or may comprise multiple sub-networks—including wirelessnetworks and the Internet. Communication network 120 typically includeswireless base stations, routers, servers, gateways, signalingprocessors, communication links, and the like.

Wireless communication links 121-123 use air or space as the transportmedium. Wireless communication links 121-123 may use various protocols,such as Code Division Multiple Access (CDMA), Global System for Mobilecommunications (GSM), High-Speed Packet Access (HSPA), Evolution-DataOptimized (EVDO), Long Term Evolution (LTE), Worldwide Interoperabilityfor Microwave Access (WiMax), IEEE 802.11 protocols (WIFI), Bluetooth(near-field), or some other wireless communication format—includingcombinations thereof. Communication links 124-127 use metal, air, space,glass, plastic, and/or some other transport material. Communicationlinks 124-126 could use various communication protocols, such as TDM,IP, Ethernet, optical networking, hybrid fiber coax (HFC), communicationsignaling, wireless protocols, or some other communicationformat—including combinations thereof. Communication links 121-127 arerepresentative and may include intermediate links, systems, andnetworks.

The above description and associated figures teach the best mode of theinvention. The following claims specify the scope of the invention. Notethat some aspects of the best mode may not fail within the scope of theinvention as specified by the claims. Those skilled in the art willappreciate that the features described above can be combined in variousways to form multiple variations of the invention. As a result, theinvention is not limited to the specific embodiment described above, butonly by the following claims and their equivalents.

What is claimed is:
 1. A method of operating a communication system toprovide access to a target wireless communication device, the methodcomprising: in the target wireless communication device, transferring anaming system registration message for delivery to a naming serversystem, wherein the naming system registration message indicates adomain name for the target wireless communication device and an accessschedule for communication with the target wireless communicationdevice; in the naming server system, receiving the naming systemregistration message transferred by the target wireless communicationdevice; in the naming server system, receiving an address request forthe domain name for the target wireless communication device; in thenaming server system, processing the domain name for the target wirelesscommunication device and the access schedule for the target wirelesscommunication device to respond with an address for the target wirelesscommunication device if a current time is within the access schedule fortarget wireless communication device; in the naming server system,processing the domain name for the target wireless communication deviceand the access schedule for the target wireless communication device torespond with a timeframe to re-send the address request if the currenttime is not within the access schedule for target wireless communicationdevice.
 2. The method of claim 1 wherein the naming server systemcomprises a Domain Naming Server (DNS).
 3. The method of claim 1 whereinthe domain name comprises a Uniform Resource Identifier (URI).
 4. Themethod of claim 1 wherein the timeframe comprises at least one timeperiod when the target wireless communication device is preconfigured toaccess the communication system.
 5. The method of claim 1 furthercomprising, in the target wireless communication device, detecting apre-determined atmospheric condition, and wherein transferring theregistration message comprises transferring the registration message inresponse to the detection of the pre-determined atmospheric condition.6. The method of claim 1 further comprising, in the target wirelesscommunication device, detecting a pre-determined wireless networkstatus, and wherein transferring the registration message comprisestransferring the registration message in response to the detection ofthe pre-determined wireless network status.
 7. The method of claim 1further comprising, in the target wireless communication device,detecting a pre-determined radio frequency network, and whereintransferring the registration message comprises transferring theregistration message in response to the detection of the pre-determinedradio frequency network.
 8. The method of claim 1 further comprising, inthe target wireless communication device, detecting presence in apre-determined geographic area, and wherein transferring theregistration message comprises transferring the registration message inresponse to the detection of the presence in the pre-determinedgeographic area.
 9. The method of claim 1 further comprising, in thetarget wireless communication device, detecting an amount of remainingbattery power for the target wireless communication device and selectingthe access schedule based on the amount of remaining battery power forthe target wireless communication device.
 10. The method of claim 1further comprising, in the target wireless communication device,detecting a power source for the target wireless communication deviceand selecting the access schedule based on the detection of the powersource for the target wireless communication device.
 11. A communicationsystem comprising: a target wireless communication device configured totransfer a naming system registration message to a naming server system,wherein the naming system registration message indicates a domain namefor the target wireless communication device and an access schedule forcommunication with the target wireless communication device; and anaming server system configured to receive the naming systemregistration and an address request for the domain name for the targetwireless communication device; and the naming server system configuredto process the domain name for the target wireless communication deviceand the access schedule for the target wireless communication device;and the naming server system configured to respond with an address forthe target wireless communication device if a current time is within theaccess schedule for the target wireless communication device or torespond with a timeframe to re-send the address request if the currenttime is not within the access schedule for the target wirelesscommunication device.
 12. The communication system of claim 11 whereinthe naming server system comprises a Domain Naming Server (DNS).
 13. Thecommunication system of claim 11 wherein the domain name comprises aUniform Resource Identifier (URI).
 14. The communication system of claim11 wherein the timeframe comprises at least one time period when thetarget wireless communication device is preconfigured to access thecommunication system.
 15. The communication system of claim 11 whereinthe target wireless communication device is configured to detect apre-determined atmospheric condition and to transfer the registrationmessage in response to the detection of the pre-determined atmosphericcondition.
 16. The communication system of claim 11 wherein the targetwireless communication device is configured to detect a pre-determinedwireless network status and to transfer the registration message inresponse to the detection of the pre-determined wireless network status.17. The communication system of claim 11 wherein the target wirelesscommunication device is configured to detect a pre-determined radiofrequency network and to transfer the registration message in responseto the detection of the pre-determined radio frequency network.
 18. Thecommunication system of claim 11 wherein the target wirelesscommunication device is configured to determine presence in apre-determined geographic area, and to transfer the registration messagein response to the detection of the presence in the pre-determinedgeographic area.
 19. The communication system of claim 11 wherein thetarget wireless communication device is configured to detect an amountof remaining battery power for the target wireless communication device,and to select the access schedule based on the amount of remainingbattery power for the target wireless communication device.
 20. Thecommunication system of claim 11 wherein the target wirelesscommunication device is configured to detect a power source for thetarget wireless communication device and to select the access schedulebased on the detection of the power source for the target wirelesscommunication device.